Skip to content

Conversation

@smishra1200
Copy link

suggestion to remove "this solution may address uses cases" -> this solution shall address use cases that may include...

suggestion to remove "this solution may address uses cases" -> this solution shall address use cases that may include...
@fluffy fluffy changed the title Update charter.md Reword covered use case language Jul 27, 2022
@fluffy
Copy link
Collaborator

fluffy commented Jul 27, 2022

What would you think of changing "shall address" to "addresses" ? I don't feel strongly about this one way or other

@smishra1200
Copy link
Author

Hi Cullen, changing "shall address" to "addresses" works for me

changed "shall address" -> addresses
@suhasHere
Copy link
Contributor

+1 on the change

hardie added a commit that referenced this pull request Aug 29, 2022
This incorporates the changes proposed #63, #64, and #68, removes the Mandatory-to-Implement section as discussed on the mailing lists, and makes the required changes to address the Block from the IESG charter discussion.

It does not address #66, Spencer's suggestion to drop the Architecture documents, or his suggestion that we specify of MoQ-capable in front of relays (and similar).
@hardie
Copy link
Collaborator

hardie commented Oct 11, 2022 via email

@smishra1200
Copy link
Author

Hi Ted - I am good with the final MOQ charter as the language is clear WRT to the statement about the use cases. The PR I raised right after the IETF 114 meeting was specifically asking to change
from: "this solution may address uses cases"
to: "this solution shall address use cases that may include..."

In the end, the final wording is even better: "This solution addresses use cases including live streaming, gaming, and media conferencing and will scale efficiently."

So, I am all good WRT my PR, however, administratively, it appears my request should have been picked as it was submitted way ahead of the IESG request and in fact, I spoke about this on the MIC in the room (the day of the BOF).

@smishra1200
Copy link
Author

smishra1200 commented Oct 11, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants